System and Method for Integrating an Outgoing Cellular Call as an Enterprise Call

ABSTRACT

A method on a wireless user equipment (UE) device facilitates integration of an outgoing cellular call as an enterprise call. The UE device attaches to a wide area cellular network on which the device has a non-enterprise address. Upon blocking incoming calls, the UE device sends a request to a node in a data network to initiate an outgoing cellular call with an expectation of receiving an incoming circuit-switched (CS) call back from the network node within a time window. The incoming CS call contains an enterprise address associated with a user of the wireless UE device as a calling line identity to identify that the incoming CS call is related to the request to initiate the outgoing cellular call. The UE device indicates to the network node that a call leg is established between the enterprise user and the network node.

PRIORITY UNDER 35 U.S.C. §119(e) & 37 C.F.R. §1.78

This non-provisional patent application is a continuation applicationclaiming the benefit of the following prior United States patentapplication of the same name filed Apr. 30, 2007, application Ser. No.11/796,915, which is (are) hereby incorporated by reference.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application discloses subject matter that is related to the subjectmatter of the following U.S. patent application(s): (i) “SYSTEM ANDMETHOD FOR PRESENTING MEDIA TO MULTIPLE PARTIES IN A SIP ENVIRONMENT”(Docket No. 30761-2-US-PAT), application Ser. No. 11/796,804, filed Apr.30, 2007, in the name(s) of Andrew Allen, Adrian Buckley, RichardGeorge, Brian Oliver, Lap Luu and Dalsu Lee; and (ii) “SYSTEM AND METHODFOR INTEGRATING AN OUTGOING CELLULAR CALL AS AN ENTERPRISE CALL IN ANIMS ENVIRONMENT”, application Ser. No. 11/796,827, filed Apr. 30, 2007,in the name(s) of Andrew Allen, Adrian Buckley, Richard George, BrianOliver, Lap Luu and Dalsu Lee, which is (are) hereby incorporated byreference.

FIELD OF THE DISCLOSURE

The present patent disclosure generally relates to communicationsnetworks. More particularly, and not by way of any limitation, thepresent patent disclosure is directed to a system and method forintegrating an outgoing cellular call as an enterprise call in a networkenvironment.

BACKGROUND

Many enterprise networks are replacing their existing Private BranchExchange (PBX)- and Central Office Exchange (CENTREX)-based telephonysystems with systems based upon Voice-over-IP (VoIP) and SessionInitiation Protocol (SIP)-based signaling systems that utilize theexisting enterprise IP infrastructure, e.g., Local Area Network (LAN)and Wireless LAN (WLAN) technologies. It is not uncommon for enterpriseemployees to regularly use mobile communications devices when away fromthe enterprise, which interoperate with cellular networks such as, e.g.,the Global System for Mobile Communications (GSM) networks, CodeDivision Multiple Access (CDMA) networks, and Universal MobileTelecommunications System (UMTS) networks, to keep in touch with otheremployees of the enterprise and to conduct business communications withother people outside the enterprise. Additionally, mobile communicationsdevices are being enhanced to provide SIP-based communications(including VoIP) over WLAN access as well as cellular networks, therebyallowing these devices to provide mobile telephony communicationscapability when within the enterprise as well as when away from theenterprise. It is expected that such developments may allow replacementof the ubiquitous wired desktop phone in the enterprise with dual-mode,WLAN-capable mobile devices.

Although cellular telephony networks have deployed IP-based datacommunications capabilities through exploitation of well-knowntechnologies, it is generally understood that these networks cannotcurrently commercially support carrier-class VoIP telephony services dueto issues of delay, Quality of Service (QoS) and efficiency, whichprevent cost-effective usage of such networks for purposes of providingacceptable quality voice services. Accordingly, for the foreseeablefuture, telephony services based upon the existing networkinfrastructure are likely to continue to utilize conventionalcircuit-switched network technology for telephony calls.

Based on the foregoing, it should appreciated that the integration ofVoIP enterprise networks with carrier cellular telephony networks inorder to serve an enterprise user within the enterprise as well as whileaway is fraught with numerous difficulties. Moreover, in such scenariosit may be desirable for enterprises to have certain control over thecalls made by their employees for tracking and monitoring purposes.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the embodiments of the present patentdisclosure may be had by reference to the following Detailed Descriptionwhen taken in conjunction with the accompanying drawings wherein:

FIG. 1 depicts an exemplary network environment wherein one or moreembodiments of the present patent disclosure may be practiced forpurposes of integrating an outgoing cellular call as an enterprise call;

FIG. 2 depicts a flowchart of the present patent disclosure according toone embodiment;

FIG. 3 depicts another flowchart of the present patent disclosureaccording to one embodiment;

FIG. 4 depicts an exemplary message flow diagram according to oneembodiment of the present patent disclosure; and

FIG. 5 depicts a block diagram of an embodiment of a communicationsdevice operable for purposes of the present patent disclosure.

DETAILED DESCRIPTION OF THE DRAWINGS

The present patent disclosure is broadly directed to a scheme forintegrating an outgoing cellular call as an enterprise call wherein anenterprise user's enterprise address is presented to the called partyinstead of the enterprise user's non-enterprise address (e.g., cellulartelephony number). In one aspect, disclosed herein is an embodiment of amethod for facilitating integration of an outgoing cellular call as anenterprise call, wherein the outgoing cellular call is originated by anenterprise user towards a called party when the enterprise user isattached to an external wide area cellular network via a mobilecommunications device, the enterprise user having an enterprise addressand a non-enterprise address. The claimed embodiment comprises: sendinga request to a network node for initiating the outgoing cellular call tothe called party with an expectation to receive an incomingcircuit-switched call back from the network node within a time window;receiving the incoming circuit-switched call from the network node andidentifying that the incoming circuit-switched call contains theenterprise address as a calling line identity; correlating that theincoming circuit-switched call is related to the request to initiateorigination of the outgoing cellular call; and providing an indicationto the network node (which could be optional in some embodiments) that acall leg is established between the enterprise user and the networknode.

In another aspect, disclosed herein is an embodiment of a method forintegrating an outgoing cellular call as an enterprise call by anenterprise user having an enterprise address and a non-enterpriseaddress. The claimed embodiment comprises: receiving a request from theenterprise user for initiating the outgoing cellular call to the calledparty; establishing a first call leg to the enterprise user by sending acircuit-switched call that identifies the enterprise address as acalling line identity; establishing a second call leg to the calledparty, preferably upon receiving an indication that the first call leghas been established; and patching the first and second call legs toestablish an end-to-end communications path between the enterprise userand the called party, wherein the enterprise address is presentedinstead of the non-enterprise address to the called party as a callingline identity with respect to the outgoing cellular call from theenterprise user.

In a further aspect, disclosed herein is an embodiment of a userequipment (UE) device operable to generate an outgoing cellular call asan enterprise call to a called party. The claimed embodiment comprises:means for sending a request to a network node to initiate origination ofthe outgoing cellular call to the called party with an expectation toreceive an incoming circuit-switched call back from the network nodewithin a time window; and means for correlating that the incomingcircuit-switched call is related to the request to initiate originationof the outgoing cellular call by identifying that the incomingcircuit-switched call contains an enterprise address of the enterpriseuser as a calling line identity.

In a still further aspect, disclosed herein is an embodiment of anetwork node for integrating an outgoing cellular call as an enterprisecall. The claimed embodiment comprises: means, responsive to receiving arequest from the enterprise user to initiate origination of the outgoingcellular call to the called party, for establishing a first call leg tothe enterprise user by sending a circuit-switched call that identifiesthe enterprise address as a calling line identity; means forestablishing a second call leg to the called party upon receiving anindication from the enterprise user that the first call leg has beenestablished; and means for patching the first and second call legs toestablish an end-to-end communications path between the enterprise userand the called party, wherein an enterprise address of the enterpriseuser instead of its non-enterprise address is presented to the calledparty as a calling line identity with respect to the outgoing cellularcall from the enterprise user.

A system and method of the present patent disclosure will now bedescribed with reference to various examples of how the embodiments canbest be made and used. Like reference numerals are used throughout thedescription and several views of the drawings to indicate like orcorresponding parts, wherein the various elements are not necessarilydrawn to scale. Referring now to the drawings, and more particularly toFIG. 1, an exemplary network environment 100 is depicted wherein anembodiment of the present patent disclosure may be practiced forintegrating an outgoing cellular call as an enterprise call. Asdepicted, the network environment 100 includes a generalized networkinfrastructure 102 wherein certain portions may form an enterprisenetwork whereas the remaining portions may comprise an external networkarrangement such as one or several service provider networks that serveas intermediary networks with respect to the enterprise network and thewell-known PSTN/PLMN infrastructure 114. For purposes herein, anenterprise network may be any communications network internal to acompany, office, or organization, and may comprise wireline and/orwireless network infrastructure. Regardless of the actualimplementation, the network infrastructure 102 includes an integrationserver (also referred to as a Unified Communications Platform (UCP)element) 104, a switching element such as a SIP-capable Private BranchExchange (PBX) 110 and a gateway (GW) element such as a SIP/PSTN GW 112.As alluded to previously, one or more of these elements may beincorporated within an enterprise network infrastructure in oneembodiment. Alternatively, one or more of these elements or theirfunctionalities may be hosted in a service provider network. In eitherarrangement, the functionalities of the elements may be integrated orredistributed into separate network entities. Accordingly, for purposesof the present patent disclosure, a “network node” may comprise ageneralized network entity that effectuates or facilitates at least aportion of the functionalities set forth hereinbelow with respect tocall integration.

An enterprise user is operable to effectuate communications (e.g.,voice/data/video calls or multimedia sessions, and the like) in a numberof scenarios within the context of the network environment 100 withrespect to a called party 120. In general, the enterprise user iscapable of initiating communications using one of two addresses: anenterprise address that may be used for calls made from within theenterprise network and a non-enterprise address for calls made fromoutside the enterprise network. In one application, the enterprise usermay be provided with two separate pieces of user equipment (UE) 118: awireline telephony equipment having the enterprise address that is usedwhen the enterprise user is on the enterprise premises and a mobilecommunications device (MCD) having a cellular telephony number (i.e.,non-enterprise address) that may be used when the enterprise user isaway. Alternatively, where local wireless connectivity to the enterprisenetwork is supported, a single wireless UE device operable in twodifferent radio access technologies (RATS) may be provided. In thisscenario, when the wireless UE device is attached to the enterprisenetwork via any known or heretofore unknown Wireless Local Area Network(WLAN) technology, calls originated by the enterprise user may have theenterprise address as the calling party number. On the other hand, callsoriginated when the wireless UE device is attached to a wide areacellular network (WACN) such as the Public Land Mobile Network (PLMN)114 may have the non-enterprise address (e.g., cellular telephonynumber) as the calling party number. Accordingly, it should beappreciated that the enterprise user equipment 118 may be a conventionalcellular phone having data channel capability (e.g., Short MessageService or SMS capability) or a dual-mode MCD having WLAN capability(for enterprise operation) and WACN capability (for remote operation).Additionally, for purposes of further generalization, the enterprise UEdevice 118 may also comprise any personal computer (e.g., desktops,laptops, palmtops, personal digital assistants (PDAs) or other handheldcomputing devices) equipped with a suitable wireless modem, as well as acommunications device operable in both circuit-switched (CS) andpacket-switched (PS) communications that may even be capable ofeffectuating an inter-technology handoff between both CS and PS domains.

Based on the foregoing, it may be realized that the enterprise andnon-enterprise addresses for an enterprise user may take on differentforms, depending on the equipment and service provisioning. Forinstance, the enterprise address may comprise a SIP Uniform ResourceIdentifier (URI) or an E-164 number. Likewise, the non-enterpriseaddress and the called party address may also comprise either SIP URIs,E.164 numbers, or other identifiers.

An enterprise data server 116 may be disposed in association with atleast a portion of the network 102, preferably with the UCP node 104when provisioned as part of an enterprise network. A data communicationspath 122 may be effectuated between the enterprise UE 118 and theenterprise network over the PLMN data network infrastructure via theenterprise data server 116. Regardless of whether integrated within anenterprise network or disposed in a service provider network, UCP node104 preferably includes a Call Manager functionality 106 as well as aSIP Back-to-Back User Agent (B2BUA) 108 that is operable to performthird-party call control in order to combine multiple call legstogether. In general, all enterprise SIP calls may be routed via the UCPnode 104 and it is the role of the UCP node 104 to trigger the routingof the incoming SIP calls to the enterprise user regardless of whetherUE 118 is attached via the enterprise WLAN or via the PLMN cellularnetwork. Further, as will be described in detail below, the enterprisedata server 116 can also receive a trigger message (i.e., a request tooriginate an outgoing cellular call) from UE 118 that is attached to thePLMN cellular network 114 via the cellular network's data network (suchas GPRS or CDMA packet data network, for example) to request that theUCP node 104 establish a call between the enterprise UE 118 and theequipment 120 of the called party.

Taking reference to FIGS. 1 and 2 together, a generalized scheme 200 forintegrating outgoing calls from the enterprise UE 118 when it isattached to the cellular network may be set forth as follows. Theenterprise user using its equipment sends a request message to a servingnetwork node (i.e., the UCP element 104 shown in FIG. 1) via thecellular network's data network (block 202). Additionally oralternatively, the request message may also be mediated via anenterprise data server. In one embodiment, the request may comprise aSIP Request such as a SIP REFER message or some other SIP Request (e.g.,a SIP INVITE message) either sent directly to the enterprise data server116 via the cellular network's data network or routed to the UCP node104 via the cellular network's SIP based infrastructure such as the IPMultimedia Subsystem (IMS). Alternatively, the message may not be a SIPMessage at all and could be any message that contains the necessaryinformation to enable the UCP node 104 to establish a call between theenterprise UE 118 and the called party's equipment 120 that theenterprise user is attempting to call (e.g., an SMS message, anUnstructured Supplementary Service Data (USSD) message, or an IP basedmessage). In accordance with an embodiment, the following pieces ofinformation may be transmitted as part of the request message: (i) theenterprise address (e.g., SIP URI or E.164 number) that the enterpriseuser is reachable at; (ii) the non-enterprise address (e.g., E.164number) that the enterprise UE is reachable at when it is attached tothe cellular network; (iii) the E.164 number or SIP URI of the calledparty; and (iv) an indication of whether privacy is required. Uponreceiving the request message from the enterprise UE (block 204), theservice logic at the UCP node 104 uses the received information toeffectuate two call legs in association with a switching node such as aSIP-capable PBX/CENTREX node, a first call leg between the switchingnode and the enterprise UE and a second call leg between the calledparty's UE and the switching node wherein the enterprise user'senterprise address is presented to the called party instead of thenon-enterprise address associated with the UE (i.e., the cellularnumber) (block 206). Thereafter, the first and second call legs arepatched together wherein the two respective Session Description Protocol(SDP) streams associated with the call legs are joined in order toestablish an end-to-end bearer communications path between theenterprise user and the called party (block 208).

Set forth below is an example of how a SIP REFER request can be used totrigger the UCP node 104 to establish an outgoing call within thecontext of the scheme described above:

TABLE I   REFER sip: IntegrationServer@companyXXX.com; SIP/2.0   Via:SIP/2.0/UDP PIN12345678.blackberry.com     ;branch=z9hG4bKhjhs8ass83  Max-Forwards: 70   To: <sip: IntegrationServer@companyXXX.com>   From:Mike <sip:Mike@companyXXX.com>;tag=32331   Call-ID: d432fa84b4c76e66710  Cseq: 2 REFER   Contact: <sip:PIN12345678.blackberry.com>   Refer-To:<cid:cn35t8jf02@companyXXX.com>   Require: multiple-refer  Content-Type: application/resource-lists+xml   Content-Disposition:recipient-list   Content-Length: 362   Content-ID:<cn35t8jf02@example.com>   <?xml version=”1.0″ encoding=”UTF-8″?>  <resource-lists xmlns+″um:ietf:params:xml:ns:resource- lists″    Xmins:xsi=″http://www.w3.org/2001/XML.Schema-instance″>   <list>  <entry uri=”tel: 098-765-4321″/>   <entry uri=”tel: 123-456-7890″/>  </list>   </resource-lists>

Those skilled in the art will recognize that the above SIP REFER requestembodiment uses the Resource List mechanism defined indraft-ietf-sip-multiple-refer and draft-ietf-simple-xcap-list-user totrigger the sending of a SIP INVITE request towards both the enterpriseUE 118 and the called party equipment 120 using the list entry urielements to deliver both the E.164 number that the enterprise UE isreachable at via the cellular network and the E.164 number of the partybeing called. Accordingly, when the UCP node 104 receives the SIP REFERrequest or other trigger message, it uses SIP Third Party Call Controlto establish two SIP Call legs; one SIP leg to the enterprise UE via thePBX, SIP-PSTN Gateway and the circuit-switched cellular network; theother SIP leg to the called party. As pointed out previously, these twocall legs are joined together at the UCP node 104 in order to form asingle end-to-end call between the enterprise user and the called party.The SIP INVITE requests sent contain the enterprise address of theenterprise UE terminal which can be in the form of SIP URI or as anE.164 number in a TEL URI along with the appropriate privacy setting ifrequested in the SIP REFER request. Alternatively, the privacy settingmay be required by the enterprise network based on certain serviceprovisioning policies and profiles. The enterprise address of theenterprise UE terminal can be transported in the SIP INVITE requestusing the SIP From header, Referred-By header, P-Asserted-Identityheader, Identity header or Remote-Party-ID header. If a SIP URI is usedas the enterprise address of the enterprise UE terminal, the SIP-PBX 110may translate this address to the corresponding E.164 number thatrepresents the enterprise address of the device. The SIP-PSTN GW 112includes the E.164 number that represents the enterprise address of theenterprise UE terminal in the Calling Line Identity in thecircuit-switched signaling messages.

With respect to the behavior of the enterprise UE for purposes offacilitating integration of an outgoing cellular call, reference may nowbe taken to FIG. 3 wherein a flowchart is depicted. When a requestmessage for initiating an outgoing cellular call to a called party istransmitted to the network infrastructure, there is an expectation toreceive an incoming circuit-switched call back from the network within atime window (block 302). Accordingly, a timer mechanism may be startedat the application level to determine when to receive thecircuit-switched call back in response to the outgoing request message.In one embodiment, if the timer expires, the enterprise UE device maytry a number of times until a limit is reached, whereupon the call isconsidered to have failed. When the enterprise UE device receives a callestablishment SETUP signaling request via the circuit-switched PSTN/PMLNsignaling, the logic executing on the device is operable to identifythat the circuit-switched call contains the enterprise address as theCalling Line Identity (block 304) (that is, the Calling Line Identity inthe SETUP is the enterprise UE's enterprise address), and based thereon,the logic determines that this incoming call is related to the requestedoutgoing call (requested via the SIP REFER request or other message)(block 306). Accordingly, the logic operates to suppress generation ofan alert to the enterprise user but establishes the circuit-switchedcall and stops the application timer (block 306). Further, theenterprise UE may provide an indication to the network that the call leghas been established (block 308). Accordingly, in one embodiment, theUCP node may wait until it receives such an acknowledgement of theestablishment of the call leg with the enterprise UE device beforeattempting to establish the call leg to the called user by sending anSIP INVITE request in order to avoid the possibility of the called partyanswering before the call leg with the enterprise UE device isestablished (i.e., avoidance of a race condition). In the meantime,until the call legs are patched, there may be a delay experienced at theenterprise UE from the time the circuit-switched call leg with thenetwork is established. Appropriate delay handling mechanisms(s) maytherefore be provided to mitigate the delay.

When the called party's equipment receives the circuit-switched SETUPmessage (or SIP INVITE request if the called party is using a SIP phonewithin the enterprise SIP network or an external SIP network), theCalling Line Identity in the case of the circuit-switched SETUP message(or From header, Referred-By header, P-Asserted-Identity header,Identity header or Remote-Party-ID header in the case of SIP INVITEmessage) contains the enterprise address (e.g., E.164 number or SIP URI)of the enterprise UE device to be presented to the called party forCalling Line Identity Presentation (if provided based on the privacysetting). The called phone rings the user and returns an ALERTINGmessage in the case of a circuit-switched call (or a SIP 180 “Ringing”response in the case of a SIP call). An ALERTING message will betranslated by the SIP-PSTN gateway to a SIP 180 “Ringing” response. Whenthe SIP 180 “Ringing” response is received at the UCP node, the servicelogic operable thereat may send a notification of “Ringing” back to theenterprise UE terminal via the cellular network's data network. In thecase that the call establishment was triggered using a SIP REFERrequest, this notification may be in the form of a SIP NOTIFY request asspecified in RFC 3515. In the case a message other than a SIP REFERrequest was used, the notification of “Ringing” may be sent using someother message. It is necessary to use the connection via the cellularnetwork's data network to notify the “Ringing” since the call leg thatis established with the enterprise UE terminal via the circuit-switchednetwork is “in the wrong direction” to be able to indicate ALERTINGusing the circuit-switched signaling protocol.

Upon answering by the enterprise user, the UE terminal sends thecircuit-switched CONNECT message (or SIP 200 “OK” response if the calledparty is using a SIP phone within the enterprise SIP network or anexternal SIP network). A CONNECT message will be translated by theSIP-PSTN GW to a SIP 200 “OK” response. When the SIP 200 “OK” responseis received at the UCP node 104, it can send a notification of “OK” backto the enterprise UE terminal via the cellular network's data network.In the case that the call establishment was triggered using a SIP REFERrequest, this notification will be in the form of a SIP NOTIFY requestas specified in RFC 3515. In the case a message other than a SIP REFERrequest was used, the notification of “OK” may be sent using some othermessage. At this point the call is established via the cellular networkbetween the enterprise UE terminal and the called party, with theenterprise address of the enterprise UE terminal being displayed as theidentity of the calling party.

FIG. 4 depicts an exemplary message flow diagram according to anembodiment of the process set forth above. As illustrated, a UCP node402 and a network node 404 are exemplified to highlight the message flowbetween the enterprise UE 118 and the network infrastructure inparticular detail. Upon blocking all incoming calls to the enterprise UE118 (block 406), a request with respect to an outgoing call is initiated(reference numeral 408). In response, the UCP node 402 sends a messageto the network node 404 (e.g., SIP-PBX) to block calls to the enterpriseUE 118. A confirmation 412 is then propagated from the network node 404to enterprise UE 118 via the UCP node 412, whereupon incoming calls fromthe network may be allowed (block 414). The UCP node 402 transmits amessage 416 to the network node 404 to invite the enterprise user (i.e.,caller) with respect to establishing a CS call 418 through the cellularnetwork to the enterprise UE 118. Service logic at the enterprise UE 118is operable to intercept the incoming CS call setup and identify thatthe enterprise address of the enterprise user is the CLI (block 420).Thereafter, a SIP 200 “OK” message 424 is generated by the network node404 towards the UCP node 402 with respect to caller SDP. In response, anacknowledgement (ACK) 426 is generated by the UCP node 402. The UCP node402 also generates a message 428 towards the network node 404 to invitethe called party (i.e., callee) with respect to establishing a CS call430 therewith through the PSTN/PLMN. As shown in block 422, appropriateservice logic may be provided for handling the delay before patching thecall legs. Pursuant to joining the audio paths (block 432), a SIP 200“OK” message 434 is generated by the network node 404 towards the UCPnode 402 with respect to callee SDP. In response, an acknowledgement(ACK) 436 is generated by the UCP node 402. A message 438 is providedthereafter by the UCP node 402 to the network node 404 in order tounblock calls to the enterprise UE 118, resulting in a confirmation 440by the network node 404. It should be appreciated that the variousoperations set forth herein may be accomplished via a number of means,including software (e.g., program code), firmware, hardware, or in anycombination, usually in association with a processing system. Where theprocesses are embodied in software, such software may comprise programinstructions that form a computer program product, uploadable serviceapplication software, or software downloadable from a remote station,and the like.

FIG. 5 depicts a block diagram of an embodiment of a communicationsdevice 500 operable as a UE device, e.g., the enterprise UE 118, forpurposes of the present patent disclosure. It will be recognized bythose skilled in the art upon reference hereto that although anembodiment of UE 118 may comprise an arrangement similar to one shown inFIG. 5, there can be a number of variations and modifications, inhardware, software or firmware, with respect to the various modulesdepicted. Further, a UE device 500 for purposes of the presentdisclosure may comprise a mobile equipment (ME) device without aremovable storage module and/or a mobile device coupled with such astorage module. Accordingly, the arrangement of FIG. 5 should be takenas illustrative rather than limiting with respect to the embodiments ofthe present patent disclosure. A microprocessor 502 providing for theoverall control of an embodiment of UE 500 is operably coupled to acommunication subsystem 504 that may preferably be capable of multi-modecommunications (e.g., CS domain and PS domain). The communicationsubsystem 504 generally includes one or more receivers 508 and one ormore transmitters 514 as well as associated components such as one ormore local oscillator (LO) modules 510 and a processing module such as adigital signal processor (DSP) 512. As will be apparent to those skilledin the field of communications, the particular design of thecommunication module 504 may be dependent upon the communicationsnetworks with which the mobile device is intended to operate (e.g., aCDMA network, a GSM network, WLAN, et cetera). Regardless of theparticular design, however, signals received by antenna 506 throughappropriate access infrastructure 505 (e.g., cellular base stationtowers, WLAN hot spots, etc.) are provided to receiver 508, which mayperform such common receiver functions as signal amplification,frequency down conversion, filtering, channel selection,analog-to-digital (A/D) conversion, and the like. Similarly, signals tobe transmitted are processed, including modulation and encoding, forexample, by DSP 512, and provided to transmitter 514 fordigital-to-analog (D/A) conversion, frequency up conversion, filtering,amplification and transmission over the air-radio interface via antenna516.

Microprocessor 502 may also interface with further device subsystemssuch as auxiliary input/output (I/O) 518, serial port 520, display 522,keyboard/keypad 524, speaker 526, microphone 528, random access memory(RAM) 530, a short-range communications subsystem 532, and any otherdevice subsystems, e.g., timer mechanisms, generally labeled asreference numeral 533. To control access, a USIM/RUIM interface 534 mayalso be provided in communication with the microprocessor 602. In oneimplementation, USIM/RUIM interface 534 is operable with a USIM/RUIMcard having a number of key configurations 544 and other information 546such as identification and subscriber-related data.

Operating system software and applicable service logic software may beembodied in a persistent storage module (i.e., non-volatile storage)such as Flash memory 535. In one implementation, Flash memory 535 may besegregated into different areas, e.g., storage area for computerprograms 536 (e.g., service processing logic), as well as data storageregions such as device state 537, address book 539, other personalinformation manager (PIM) data 541, and other data storage areasgenerally labeled as reference numeral 543. A transport stack 545 may beprovided to effectuate one or more appropriate radio-packet transportprotocols. In addition, enterprise call request messaging logic 548,including memory storage for storing pertinent address information, isprovided for facilitating integration of outgoing calls as set forthhereinabove.

It is believed that the operation and construction of the embodiments ofthe present patent application will be apparent from the DetailedDescription set forth above. While the exemplary embodiments shown anddescribed may have been characterized as being preferred, it should bereadily understood that various changes and modifications could be madetherein without departing from the scope of the present disclosure asset forth in the following claims.

What is claimed is:
 1. A method, operable on a wireless user equipment(UE) device, for facilitating integration of an outgoing cellular callas an enterprise call, comprising: attaching to a wide area cellularnetwork on which said wireless UE device has a non-enterprise address;upon blocking all incoming calls to the UE device, sending a datarequest to a network node in a data network for initiating an outgoingcellular call to a called party with an expectation to receive anincoming circuit-switched call back from said network node within a timewindow; receiving said incoming circuit-switched call from said networknode, said incoming call containing an enterprise address associatedwith a user of said wireless UE device as a calling line identity toidentify that said incoming circuit-switched call is related to saidrequest to initiate origination of said outgoing cellular call; andproviding an indication to said network node that a call leg isestablished between said enterprise user and said network node.
 2. Themethod as recited in claim 1, wherein said data request is sent as oneof a Short Message Service (SMS) message and an UnstructuredSupplementary Service Data (USSD)-based message.
 3. The method asrecited in claim 1, wherein said data request is sent as one of aSession Initiation Protocol (SIP) message and an Internet Protocol(IP)-based message.
 4. The method as recited in claim 1, wherein saiddata request includes said enterprise address, said non-enterpriseaddress, said called party's address, and a privacy indication.
 5. Themethod as recited in claim 1, wherein said enterprise address comprisesone of a SIP Uniform Resource Identifier (URI) and an E-164 number. 6.The method as recited in claim 1, wherein said non-enterprise addresscomprises a cellular telephony network number in E-164 format.
 7. Themethod as recited in claim 1, wherein said time window is effectuatedbased on commencing a timer with respect to sending said request, saidtimer being terminated upon receipt of said incoming circuit-switchedcall from said network node.
 8. A wireless user equipment (UE) deviceoperable to facilitate integration of an outgoing cellular call as anenterprise call, comprising: a component configured to attach to a widearea cellular network on which said wireless UE device has anon-enterprise address; a component configured to send a data request toa network node in a data network to initiate origination of an outgoingcellular call to a called party with an expectation to receive anincoming circuit-switched call back from said network node within a timewindow, said request being sent upon blocking all incoming calls to theUE device; a component configured to receive said incomingcircuit-switched call from said network node, said incoming callcontaining an enterprise address associated with a user of said wirelessUE device as a calling line identity to identify that said incomingcircuit-switched call is related to said request to initiate originationof said outgoing cellular call; and a component configured to indicateto said network node that a call let is established between saidwireless UE device and said network node.
 9. The UE device as recited inclaim 8, wherein said data request comprises one of a Short MessageService (SMS) message and an Unstructured Supplementary Service Data(USSD)-based message.
 10. The UE device as recited in claim 8, whereinsaid data request comprises one of a Session Initiation Protocol (SIP)REFER message, a SIP INVITE message, and an Internet Protocol (IP)-basedmessage.
 11. The UE device as recited in claim 8, wherein said datarequest includes said enterprise address, said non-enterprise address,said called party's address, and a privacy indication.
 12. The UE deviceas recited in claim 8, wherein said enterprise address comprises one ofa SIP Uniform Resource Identifier (URI) and an E-164 number.
 13. The UEdevice as recited in claim 8, wherein said non-enterprise addresscomprises a cellular telephony network number in E-164 format.
 14. TheUE device as recited in claim 8, wherein said time window is effectuatedbased on commencing a timer with respect to sending said request, saidtimer being terminated upon receipt of said incoming circuit-switchedcall from said network node.
 15. A method, operable at a network node ina data network, for integrating an outgoing cellular call from awireless user equipment (UE) device as an enterprise call, comprising:upon receiving a data request from said wireless UE device to initiatesaid outgoing cellular call to a called party, blocking all incomingcalls to the mobile communications device, said data request comprisinga non-enterprise address by which said UE device is addressed on a widearea cellular network, an enterprise address associated with a user ofsaid wireless UE device and an address for said called party;establishing a first call leg to said wireless UE device by sending acircuit-switched call containing said enterprise address as a callingline identity to identify that said circuit-switched call is related tosaid request; establishing a second call leg to said called party uponreceiving an indication that said first call leg has been established;and patching said first and second call legs to establish an end-to-endcommunications path between said wireless UE device and said calledparty, wherein said enterprise address is presented instead of saidnon-enterprise address to said called party as a calling line identitywith respect to said outgoing cellular call from said wireless UEdevice.
 16. The method as recited in claim 15, wherein said data requestis received as one of a Short Message Service (SMS) message and anUnstructured Supplementary Service Data (USSD)-based message.
 17. Themethod as recited in claim 15, wherein said data request is received asone of a Session Initiation Protocol (SIP) message and an InternetProtocol (IP)-based message.
 18. The method as recited in claim 15,wherein said enterprise address comprises one of a SIP Uniform ResourceIdentifier (URI) and an E-164 number.
 19. The method as recited in claim15, wherein said non-enterprise address comprises a cellular telephonynetwork number in E-164 format.